Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@config/templates/org-member-added.html`:
- Line 2: The template has an empty <title></title> in org-member-added.html
which fails lint; update the <title> element to a meaningful, non-empty string
(e.g., "You're invited to join {{orgName}}" or another appropriate template
variable) so the HTML title-require rule passes; modify the <title> tag in the
file to include that static text or interpolation and keep any existing head
structure unchanged.

In `@modules/organizations/services/organizations.membership.service.js`:
- Around line 491-500: Current code reads the membership with
MembershipRepository.get and later calls MembershipRepository.remove, which
risks a race where the membership's status changes between read and delete;
replace the two-step read+remove with a single atomic delete constrained by _id
+ userId + status:PENDING + source:OWNER_ADD (use membershipId and
decliningUserId and MEMBERSHIP_STATUSES.PENDING + PENDING_SOURCES.OWNER_ADD) so
the delete only succeeds if the document is still pending-owner-add and returns
the removed document (or null) in one operation (e.g., use a findOneAndDelete /
deleteOne returning document method on MembershipRepository or add an atomic
method to the repository if missing), and then return that result instead of
calling remove after get.

In `@modules/organizations/tests/organizations.decline.e2e.tests.js`:
- Around line 25-36: The JSDoc for the named helper functions is missing
`@returns` tags; update the JSDoc for resetOrgConfig to include an explicit
"`@returns` {void} Resets organizations config to original state." and update the
JSDoc for the async cleanupUser helper to include an explicit "`@returns`
{Promise<void>} Resolves when the user and associated organizations/memberships
are cleaned up." — ensure these tags are added to the existing comment blocks
above the resetOrgConfig and cleanupUser function declarations.

In
`@modules/organizations/tests/organizations.membership.addMember.email.unit.tests.js`:
- Around line 100-117: Add assertions to ensure org DB reads are skipped in the
two tests that verify sendMail is not called: in the test named "mailer NOT
configured: creates the membership and never calls sendMail" and in the test
named "user without an email: creates the membership and never calls sendMail",
add expect(mockOrgGet).not.toHaveBeenCalled() after the existing
expect(mockSendMail).not.toHaveBeenCalled(); this locks in the DB-read guard so
MembershipService.addMember (the function under test) cannot silently call
mockOrgGet when emails are not being sent.